Micron Document
<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Middleware (distributed applications)</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Middleware_(distributed_applications)"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Middleware_distributed_applications rootpage-Middleware_distributed_applications skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Middleware (distributed applications)</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr">
<style data-mw-deduplicate="TemplateStyles:r1236090951">
/* start https://en.wikipedia.org/ */


.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}


/* end https://en.wikipedia.org/ */
</style><div role="note" class="hatnote navigation-not-searchable">This article is about distributed applications. For middleware in general, see <a href="Middleware" title="Middleware">Middleware</a>.</div>
<p><b>Middleware</b> in the context of <a href="Distributed_application" class="mw-redirect" title="Distributed application">distributed applications</a> is <a href="Software" title="Software">software</a> that provides services beyond those provided by the <a href="Operating_system" title="Operating system">operating system</a> to enable the various components of a distributed system to communicate and manage data. Middleware supports and simplifies complex <a href="Distributed_application" class="mw-redirect" title="Distributed application">distributed applications</a>. It includes <a href="Web_server" title="Web server">web servers</a>, <a href="Application_server" title="Application server">application servers</a>, messaging and similar tools that support application development and delivery. Middleware is especially integral to modern information technology based on <a href="XML" title="XML">XML</a>, <a href="SOAP" title="SOAP">SOAP</a>, <a href="Web_service" title="Web service">Web services</a>, and <a href="Service-oriented_architecture" title="Service-oriented architecture">service-oriented architecture</a>.
</p><p>Middleware often enables <a href="Interoperability" title="Interoperability">interoperability</a> between applications that run on different operating systems, by supplying services so the application can exchange data in a standards-based way. Middleware sits "in the middle" between <a href="Application_software" title="Application software">application software</a> that may be working on different <a href="Operating_system" title="Operating system">operating systems</a>. It is similar to the middle layer of a <a href="Multitier_architecture" title="Multitier architecture">three-tier</a> single system architecture, except that it is stretched across multiple systems or applications. Examples include <a href="Enterprise_Application_Integration" class="mw-redirect" title="Enterprise Application Integration">EAI</a> software, telecommunications software, <a href="Transaction_Processing_System" class="mw-redirect" title="Transaction Processing System">transaction monitors</a>, and messaging-and-queueing software.
</p><p>The distinction between operating system and middleware functionality is, to some extent, arbitrary. While core kernel functionality can only be provided by the operating system itself, some functionality previously provided by separately sold middleware is now integrated in operating systems. A typical example is the <a href="TCP/IP" class="mw-redirect" title="TCP/IP">TCP/IP</a> stack for telecommunications, nowadays included virtually in every operating system.
</p>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="Definitions">Definitions</h2></div>
<p>Middleware is defined as software that provides a link between separate software applications. It is sometimes referred to as plumbing because it connects two applications and passes data between them. Middleware allows data contained in one database to be accessed through another. This makes it particularly useful for <a href="Enterprise_application_integration" title="Enterprise application integration">enterprise application integration</a> and <a href="Data_integration" title="Data integration">data integration</a> tasks.
</p><p>In more abstract terms, middleware is "The software layer that lies between the <a href="Operating_system" title="Operating system">operating system</a> and applications on each side of a distributed computing system in a network."<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="Origins">Origins</h2></div>
<p>Middleware gained popularity in the 1980s as a solution to the problem of how to link newer applications to older legacy systems, although the term had been in use since 1968.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> It also facilitated <a href="Distributed_processing" class="mw-redirect" title="Distributed processing">distributed processing</a>, the connection of multiple applications to create a larger application, usually over a network.
</p>
<div class="mw-heading mw-heading2"><h2 id="Use">Use</h2></div>
<p>Middleware services provide a more functional set of <a href="Application_programming_interface" class="mw-redirect" title="Application programming interface">application programming interfaces</a> to allow an application to:
</p>
<ul><li>Locate transparently across the network, thus providing interaction with another service or application</li>
<li>Filter data to make them friendly usable or public via <a href="Anonymization" class="mw-redirect" title="Anonymization">anonymization process</a> for privacy protection (for example)</li>
<li>Be independent from network services</li>
<li>Be reliable and always available</li>
<li>Add complementary attributes like <a href="Semantics" title="Semantics">semantics</a></li></ul>
<p>when compared to the operating system and network services.
</p><p>Middleware offers some unique technological advantages for business and industry. For example, traditional database systems are usually deployed in closed environments where users access the system only via a restricted network or <a href="Intranet" title="Intranet">intranet</a> (e.g., an enterprise’s internal network). With the phenomenal growth of the <a href="World_Wide_Web" title="World Wide Web">World Wide Web</a>, users can access virtually any database for which they have proper access rights from anywhere in the world. Middleware addresses the problem of varying levels of <a href="Interoperability" title="Interoperability">interoperability</a> among different database structures. Middleware facilitates transparent access to legacy <a href="Database_management_system" class="mw-redirect" title="Database management system">database management systems</a> (DBMSs) or applications via a <a href="Web_server" title="Web server">web server</a> without regard to database-specific characteristics.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>
</p><p>Businesses frequently use middleware applications to link information from departmental databases, such as payroll, sales, and accounting, or databases housed in multiple geographic locations.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> In the highly competitive healthcare community, laboratories make extensive use of middleware applications for <a href="Data_mining" title="Data mining">data mining</a>, <a href="Laboratory_information_system" class="mw-redirect" title="Laboratory information system">laboratory information system</a> (LIS) backup, and to combine systems during hospital mergers. Middleware helps bridge the gap between separate LISs in a newly formed healthcare network following a hospital buyout.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>
</p><p>Middleware can help software developers avoid having to write <a href="Application_programming_interface" class="mw-redirect" title="Application programming interface">application programming interfaces</a> (API) for every control program, by serving as an independent programming interface for their applications.
For <a href="Future_Internet" title="Future Internet">Future Internet</a> network operation through traffic monitoring in <a href="Network_management" title="Network management">multi-domain scenarios</a>, using mediator tools (middleware) is a powerful help since they allow <a href="Telecommunications_service_provider" class="mw-redirect" title="Telecommunications service provider">operators</a>, searchers and <a href="Service_providers" class="mw-redirect" title="Service providers">service providers</a> to supervise <a href="Quality_of_service" title="Quality of service">Quality of service</a> and analyse eventual failures in <a href="Telecommunication_service" class="mw-redirect" title="Telecommunication service">telecommunication services</a>.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> The Middleware stack is devised of several components (CSMS, TV Statistics &amp; Client applications). It is known as the software brains of OTT platforms as it controls and interconnects all the components of the solution. The Content and Subscriber Management System (CSMS) is the central part of the solution commonly referred to as an administration portal. Apart from being the main interface for operator personnel to administer the TV service (Subscribers, Content, Packages, etc.) it also controls the majority of TV services and interacts with streaming &amp; CDN and DRM serves to deliver Live, VOD and recorded content to the end users. It also integrates with external systems for billing, provisioning and with EPG and VOD content providers. Client applications authorize the CSMS and communicate with it, to provide required TV services to the end users on different devices. <sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>
</p><p>Finally, e-commerce uses middleware to assist in handling rapid and secure transactions over many different types of computer environments.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> In short, middleware has become a critical element across a broad range of industries, thanks to its ability to bring together resources across dissimilar networks or computing platforms.
</p><p>In 2004 members of the <a href="European_Broadcasting_Union" title="European Broadcasting Union">European Broadcasting Union</a> (EBU) carried out a study of Middleware with respect to system integration in broadcast environments. This involved system design engineering experts from 10 major European broadcasters working over a 12-month period to understand the effect of predominantly software-based products to media production and broadcasting system design techniques. The resulting reports Tech 3300 and Tech 3300s were published and are freely available from the EBU web site.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="Types">Types</h2></div>
<div class="mw-heading mw-heading3"><h3 id="Message-oriented_middleware">Message-oriented middleware</h3></div>
<p><a href="Message-oriented_middleware" title="Message-oriented middleware">Message-oriented middleware</a> (MOM) <sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> is middleware where transactions or event notifications are delivered between disparate systems or components by way of messages, often via an <a href="Enterprise_messaging_system" title="Enterprise messaging system">enterprise messaging system</a>. With MOM, messages sent to the client are collected and stored until they are acted upon, while the client continues with other processing.
</p>
<dl><dt>Enterprise messaging</dt>
<dd>An <a href="Enterprise_messaging_system" title="Enterprise messaging system">enterprise messaging system</a> is a type of middleware that facilitates message passing between disparate systems or components in standard formats, often using <a href="XML" title="XML">XML</a>, <a href="SOAP" title="SOAP">SOAP</a> or <a href="Web_services" class="mw-redirect" title="Web services">web services</a>. As part of an enterprise messaging system, <a href="Message_broker" title="Message broker">message broker</a> software may queue, duplicate, translate and deliver messages to disparate systems or components in a messaging system.</dd></dl>
<dl><dt>Enterprise service bus</dt>
<dd><a href="Enterprise_service_bus" title="Enterprise service bus">Enterprise service bus</a> (ESB) is defined by the <a href="Burton_Group" class="mw-redirect" title="Burton Group">Burton Group</a><sup id="cite_ref-ms-on-esb_12-0" class="reference"><a href="#cite_note-ms-on-esb-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup> as "some type of integration middleware product that supports both <a href="Message-oriented_middleware" title="Message-oriented middleware">message-oriented middleware</a> and <a href="Web_services" class="mw-redirect" title="Web services">Web services</a>".</dd></dl>
<div class="mw-heading mw-heading3"><h3 id="Intelligent_middleware">Intelligent middleware</h3></div>
<p><sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup>
Intelligent <a href="Middleware" title="Middleware">Middleware</a> (IMW) provides real-time intelligence and event management through <a href="Intelligent_agents" class="mw-redirect" title="Intelligent agents">intelligent agents</a>. The IMW manages the real-time processing of high volume sensor signals and turns these signals into intelligent and actionable business information. The actionable information is then delivered in end-user power dashboards to individual users or is pushed to systems within or outside the enterprise. It is able to support various heterogeneous types of hardware and software and provides an API for interfacing with external systems. It should have a highly scalable, <a href="Distributed_architecture" class="mw-redirect" title="Distributed architecture">distributed architecture</a> which embeds intelligence throughout the network to transform raw data systematically into actionable and relevant knowledge. It can also be packaged with tools to view and manage operations and build advanced network applications most effectively.
</p>
<div class="mw-heading mw-heading3"><h3 id="Content-centric_middleware">Content-centric middleware</h3></div>
<p>Content-centric middleware offers a simple <i>provider-consumer</i> abstraction through which applications can issue requests for uniquely identified content, without worrying about where or how it is obtained. Juno is one example, which allows applications to generate content requests associated with high-level delivery requirements.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> The middleware then adapts the underlying delivery to access the content from sources that are best suited to matching the requirements. This is therefore similar to <a href="Publish/subscribe" class="mw-redirect" title="Publish/subscribe">Publish/subscribe</a> middleware, as well as the <a href="Content-centric_networking" class="mw-redirect" title="Content-centric networking">Content-centric networking</a> paradigm.
</p>
<dl><dt>Remote procedure call</dt>
<dd><a href="Remote_procedure_call" title="Remote procedure call">Remote procedure call</a> middleware enables a client to use services running on remote systems. The process can be <a href="Synchronization_(computer_science)" title="Synchronization (computer science)">synchronous</a> or <a href="Asynchrony_(computer_programming)" title="Asynchrony (computer programming)">asynchronous</a>.</dd>
<dt>Object request broker</dt>
<dd>With <a href="Object_request_broker" title="Object request broker">object request broker</a> middleware, it is possible for applications to send objects and request services in an object-oriented system.</dd>
<dt>SQL-oriented data access</dt>
<dd>SQL-oriented Data Access is middleware between applications and database servers.</dd>
<dt>Embedded middleware</dt>
<dd>Embedded middleware provides communication services and software/<a href="Firmware" title="Firmware">firmware</a> integration interface that operates between embedded applications, the embedded operating system, and external applications.</dd></dl>
<div class="mw-heading mw-heading3"><h3 id="Policy_Appliances">Policy Appliances</h3></div>
<p>Policy appliance is a generic term referring to any form of middleware that manages policy rules. They can mediate between data owners or producers, data aggregators, and data users. Among heterogeneous institutional systems or networks they may be used to enforce, reconcile, and monitor agreed information management policies and laws across systems (or between jurisdictions) with divergent information policies or needs. Policy appliances can interact with smart data (data that carries with it contextual relevant terms for its own use), <a href="Intelligent_agent" title="Intelligent agent">intelligent agents</a> (queries that are self-credentialed, authenticating, or contextually adaptive), or <a href="Context_awareness" title="Context awareness">context-aware</a> applications to control information flows, protect security and confidentiality, and maintain privacy. Policy appliances support policy-based information management processes by enabling rules-based processing, selective disclosure, and accountability and oversight.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>
</p><p>Examples of policy appliance technologies for rules-based processing include analytic filters, <a href="Contextual_searching" title="Contextual searching">contextual search</a>, semantic programs, labeling and wrapper tools, and <a href="Digital_rights_management" title="Digital rights management">DRM</a>, among others; policy appliance technologies for selective disclosure include anonymization, content personalization, subscription and publishing tools, among others; and, policy appliance technologies for accountability and oversight include <a href="Authentication" title="Authentication">authentication</a>, authorization, immutable and non-repudiable logging, and audit tools, among others.
</p>
<div class="mw-heading mw-heading3"><h3 id="Other">Other</h3></div>
<p>Other sources include these additional classifications:
</p>
<ul><li><a href="Transaction_Processing_System" class="mw-redirect" title="Transaction Processing System">Transaction processing monitors</a>&nbsp;– provides tools and an environment to develop and <a href="Software_deployment" title="Software deployment">deploy</a> <a href="Distributed_application" class="mw-redirect" title="Distributed application">distributed applications</a>.<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup></li>
<li><a href="Application_server" title="Application server">Application servers</a>&nbsp;– software installed on a computer to facilitate the serving (running) of other applications.<sup id="cite_ref-17" class="reference"><a href="#cite_note-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup></li></ul>
<div class="mw-heading mw-heading2"><h2 id="Integration_Levels">Integration Levels</h2></div>
<div class="mw-heading mw-heading3"><h3 id="Data_Integration">Data Integration</h3></div>
<ul><li>Integration of data resources like files and databases</li></ul>
<div class="mw-heading mw-heading3"><h3 id="Cloud_Integration">Cloud Integration</h3></div>
<ul><li>Integration between various cloud services</li></ul>
<div class="mw-heading mw-heading3"><h3 id="B2B_Integration">B2B Integration</h3></div>
<ul><li>Integration of data resources and partner interfaces</li></ul>
<div class="mw-heading mw-heading3"><h3 id="Application_Integration">Application Integration</h3></div>
<ul><li>Integration of applications managed by a company</li></ul>
<div class="mw-heading mw-heading2"><h2 id="Vendors">Vendors</h2></div>
<p><a href="IBM" title="IBM">IBM</a>, <a href="Red_Hat" title="Red Hat">Red Hat</a>, <a href="Oracle_Corporation" title="Oracle Corporation">Oracle Corporation</a> and <a href="Microsoft" title="Microsoft">Microsoft</a> are some of the vendors that provide middleware software. Vendors such as <a href="Axway" class="mw-redirect" title="Axway">Axway</a>, <a href="SAP_AG" class="mw-redirect" title="SAP AG">SAP</a>, <a href="TIBCO" class="mw-redirect" title="TIBCO">TIBCO</a>, <a href="Informatica" title="Informatica">Informatica</a>, <a href="Objective_Interface_Systems" title="Objective Interface Systems">Objective Interface Systems</a>, <a href="Pervasive_Software" title="Pervasive Software">Pervasive</a>, ScaleOut Software and <a href="WebMethods" title="WebMethods">webMethods</a> were specifically founded to provide more niche middleware solutions. Groups such as the <a href="Apache_Software_Foundation" class="mw-redirect" title="Apache Software Foundation">Apache Software Foundation</a>, <a href="Opensaf" class="mw-redirect" title="Opensaf">OpenSAF</a>, the <a href="ObjectWeb" class="mw-redirect" title="ObjectWeb">ObjectWeb Consortium</a> (now OW2) and OASIS' <a href="AMQP" class="mw-redirect" title="AMQP">AMQP</a> encourage the development of <a href="Open-source_software" title="Open-source software">open source</a> middleware. Microsoft .NET "Framework" architecture is essentially "Middleware" with typical middleware functions distributed between the various products, with most inter-computer interaction by industry standards, open APIs or RAND software licence. <a href="Solace_Corporation" title="Solace Corporation">Solace</a> provides middleware in purpose-built hardware for implementations that may experience scale. StormMQ provides <a href="Message_Oriented_Middleware" class="mw-redirect" title="Message Oriented Middleware">Message Oriented Middleware</a> as a service.
</p>
<div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2></div>
<ul><li><a href="Comparison_of_business_integration_software" title="Comparison of business integration software">Comparison of business integration software</a></li>
<li><a href="Middleware_Analysts" class="mw-redirect" title="Middleware Analysts">Middleware Analysts</a></li>
<li><a href="Service-oriented_architecture" title="Service-oriented architecture">Service-oriented architecture</a></li>
<li><a href="Enterprise_Service_Bus" class="mw-redirect" title="Enterprise Service Bus">Enterprise Service Bus</a></li>
<li><a href="Event-driven_SOA" title="Event-driven SOA">Event-driven SOA</a></li>
<li><a href="ObjectWeb" class="mw-redirect" title="ObjectWeb">ObjectWeb</a></li></ul>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */


.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}


/* end https://en.wikipedia.org/ */
</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">
<ol class="references">
<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */


.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}


/* end https://en.wikipedia.org/ */
</style><cite id="CITEREFKrakowiak" class="citation web cs1">Krakowiak, Sacha. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20050507151935/http://middleware.objectweb.org/">"What's middleware?"</a>. ObjectWeb.org. Archived from <a rel="nofollow" class="external text" href="http://middleware.objectweb.org/">the original</a> on 2005-05-07<span class="reference-accessdate">. Retrieved <span class="nowrap">2005-05-06</span></span>.</cite></span>
</li>
<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite id="CITEREFGall2005" class="citation web cs1">Gall, Nick (July 30, 2005). <a rel="nofollow" class="external text" href="http://ironick.typepad.com/ironick/2005/07/update_on_the_o.html">"Update on the origin of the term "middleware""</a>.</cite></span>
</li>
<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">Peng, C, Chen, S, Chung, J, Roy-Chowdhury, A, and Srinivasan, V. (1998). Accessing
existing business data from the World Wide Web. IBM Systems Journal, 37(1), 115-132.
Retrieved March 7, 2009, from ABI/INFORM Global database. (Document ID: 26217517)</span>
</li>
<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">Bougettaya, A, Malik, Z, Rezgui, A, and Korff, L. (2006). A Scalable Middleware for Web
Databases. Journal of Database Management, 17(4), 20-39,41-46. Retrieved March 7,
2009, from ABI/INFORM Global database. (Document ID: 1155773301).</span>
</li>
<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text">Bagwell, H. (2008). <a rel="nofollow" class="external text" href="http://www.devicelink.com/ivdt/archive/08/07/007.html">Middleware: providing value beyond autoverification</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20091012130823/http://www.devicelink.com/ivdt/archive/08/07/007.html">Archived</a> 2009-10-12 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. IVDT. Retrieved March 3, 2009. .</span>
</li>
<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite id="CITEREFKai_Oswald_Seidler" class="citation web cs1">Kai Oswald Seidler. <a rel="nofollow" class="external text" href="http://www.fp7-moment.eu/">"MOMENT"</a>. Fp7-moment.eu<span class="reference-accessdate">. Retrieved <span class="nowrap">2010-08-19</span></span>.</cite></span>
</li>
<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite id="CITEREFPirtovsek2021" class="citation web cs1">Pirtovsek, Nino (September 16, 2021). <a rel="nofollow" class="external text" href="https://www.uniqcast.com/blog/ott-technology-guide-network-operators">"Guide to OTT Technology For Network Operators"</a>. <i>Uniqcast</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20221208133529/https://www.uniqcast.com/blog/ott-technology-guide-network-operators">Archived</a> from the original on December 8, 2022<span class="reference-accessdate">. Retrieved <span class="nowrap">May 10,</span> 2023</span>.</cite></span>
</li>
<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text">Charles, J. (1999). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/Xplore/login.jsp?url=%2Fielx5%2F2%2F16523%2F00762786.pdf&amp;authDecision=-203">Middleware moves to the forefront</a> <span style="font-size:0.95em; font-size:95%; color: var( --color-subtle, #555 )">(subscription required)</span>. Technology News. Retrieved March 2, 2009.</span>
</li>
<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://tech.ebu.ch/docs/tech/tech3300.pdf">"EBU middleware report Tech 3300"</a> <span class="cs1-format">(PDF)</span><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-08-19</span></span>.</cite></span>
</li>
<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://tech.ebu.ch/docs/tech/tech3300s.pdf">"EBU middleware reports Tech 3300s"</a> <span class="cs1-format">(PDF)</span><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-08-19</span></span>.</cite></span>
</li>
<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text">Curry, Edward. 2004. <a rel="nofollow" class="external text" href="http://www.mendeley.com/download/public/1652511/4338215212/cce0f06f047faa57879a1fc36a8e8d6d754d2f6a/dl.pdf">"Message-Oriented Middleware"</a> . In Middleware for Communications, ed. Qusay H Mahmoud, 1-28. Chichester, England: John Wiley and Sons. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1002%2F0470862084.ch1">10.1002/0470862084.ch1</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&nbsp;<bdi>978-0-470-86206-3</bdi></span>
</li>
<li id="cite_note-ms-on-esb-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-ms-on-esb_12-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/aa475433(BTS.10).aspx">"Microsoft on the Enterprise Service Bus (ESB)"</a>. August 2005. <q>The ESB label simply implies that a product is some type of integration middleware product that supports both MOM and Web services protocols.</q></cite></span>
</li>
<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.cougaarsoftware.com/files/CSI_ActiveEdge.pdf">Choosing the Right Middleware</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120402121113/http://www.cougaarsoftware.com/files/CSI_ActiveEdge.pdf">Archived</a> 2012-04-02 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> </span>
</li>
<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.dcs.kcl.ac.uk/staff/tysong/files/PhD.pdf">Juno</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110426045143/http://www.dcs.kcl.ac.uk/staff/tysong/files/PhD.pdf">Archived</a> 2011-04-26 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> , Gareth Tyson, A Middleware Approach to Building Content-Centric Applications. PhD Thesis, Lancaster University (2010).</span>
</li>
<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><cite class="citation cs2"><a rel="nofollow" class="external text" href="https://doi.org/10.1109/9780470874103.ch22">"Designing Technical Systems to Support Policy: Enterprise Architecture, Policy Appliances, and Civil Liberties"</a>, <i>Emergent Information Technologies and Enabling Policies for Counter-Terrorism</i>, IEEE, 2010, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&nbsp;<bdi>978-0-470-87410-3</bdi><span class="reference-accessdate">, retrieved <span class="nowrap">2025-04-28</span></span></cite></span>
</li>
<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text"><cite id="CITEREFGerndt2002" class="citation book cs1">Gerndt, Michael (2002). <i>Performance-Oriented Application Development for Distributed Architectures: Perspectives for Commercial and Scientific Environments</i>. IOS PR, Inc. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&nbsp;<bdi>978-1586032678</bdi>.</cite></span>
</li>
<li id="cite_note-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-17">^</a></b></span> <span class="reference-text"><cite id="CITEREFDong2007" class="citation book cs1">Dong, Jielin (2007). <i>Network Dictionary</i>. Javvin Press. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&nbsp;<bdi>978-1602670006</bdi>.</cite></span>
</li>
</ol></div>
<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1290876196">
/* start https://en.wikipedia.org/ */


.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}


/* end https://en.wikipedia.org/ */
</style><style data-mw-deduplicate="TemplateStyles:r1237033735">
/* start https://en.wikipedia.org/ */


@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}


/* end https://en.wikipedia.org/ */
</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">
/* start https://en.wikipedia.org/ */


.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}


/* end https://en.wikipedia.org/ */
</style>
<div class="side-box-flex">
<div class="side-box-image"><span class="noviewer" typeof="mw:File"></span></div>
<div class="side-box-text plainlist">Look up <i><b><a href="https://en.wiktionary.org/wiki/Special:Search/middleware_(distributed_applications)" class="extiw external" title="wiktionary:Special:Search/middleware (distributed applications)">middleware (distributed applications)</a></b></i> in Wiktionary, the free dictionary.</div></div>
</div>
<ul><li><a rel="nofollow" class="external text" href="http://middleware.internet2.edu/">Internet2 Middleware Initiative</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20050723082700/http://middleware.internet2.edu/">Archived</a> 2005-07-23 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></li>
<li><a rel="nofollow" class="external text" href="http://www.swami.se/">SWAMI - Swedish Alliance for Middleware Infrastructure</a></li>
<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20040220065312/http://www.omii.ac.uk/">Open Middleware Infrastructure Institute (OMII-UK)</a></li>
<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20191213122020/https://www.srinsofttech.com/what-are-the-levels-in-the-middleware-integration.html">Middleware Integration Levels</a></li>
<li><a rel="nofollow" class="external text" href="http://tech.ebu.ch/docs/tech/tech3300.pdf">European Broadcasting Union Middleware report</a>.</li>
<li><a rel="nofollow" class="external text" href="http://tech.ebu.ch/docs/tech/tech3300s.pdf">More detailed supplement to the European Broadcasting Union Middleware report</a>.</li>
<li><a rel="nofollow" class="external text" href="http://www.ow2.org/">ObjectWeb - international community developing open-source middleware</a></li></ul></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2025-04-28" href="https://en.wikipedia.org/wiki/?title=Middleware_(distributed_applications)&amp;oldid=1287728944">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>

</body></html>